Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@frontend/src/components/AdminExcelUpload/AdminExcelUpload.jsx`:
- Around line 74-77: The resetFile function only clears React state
(setSelectedFile and setUploadResult) but must also clear the underlying <input
type="file"> value so selecting the same file again triggers onChange; add a ref
for the file input (e.g., fileInputRef via useRef) in the AdminExcelUpload
component and, inside resetFile, set fileInputRef.current.value = '' (guarding
for null) after resetting state so the native input is cleared as well.

In `@frontend/src/components/AdminExcelUpload/AdminExcelUploadHeader.jsx`:
- Around line 39-42: The button in AdminExcelUploadHeader.jsx calls
onDownloadTemplate directly which will throw if the prop is undefined; update
the component to defensively handle missing prop by invoking onDownloadTemplate
only when defined (e.g. guard in the onClick handler) and optionally disable the
button (or provide a default no-op) when onDownloadTemplate is not passed so
clicks are safe; reference the onDownloadTemplate prop and the button element
with className styles.ghostButton when making the change.

In `@frontend/src/components/AdminHome/DashboardStats.jsx`:
- Around line 1-13: DashboardStats currently assumes styles is provided and will
throw when accessing styles.statsGrid; update the component signature or
destructuring to provide a safe default for styles (e.g., styles = {}) so
references like styles.statsGrid, styles.card, styles.cardTitle,
styles.cardValue, and styles.cardDescription cannot cause a TypeError, and
optionally add PropTypes to declare styles as an object (or required) to make
the contract explicit.

In `@frontend/src/components/AdminHome/MembersPanel.jsx`:
- Around line 3-7: MembersPanel accesses styles directly (e.g.,
className={styles.panel}, styles.panelHeader, styles.panelTitle) which throws if
styles is undefined; fix by providing a safe default for the styles prop (for
example set styles = {} in the component signature or initialize a fallback
const like const safeStyles = styles || {}) and then use that safeStyles (or
keep using styles after defaulting) so className lookups never read from
undefined.

In `@frontend/src/components/AdminHome/RecentActivitiesPanel.jsx`:
- Around line 1-17: RecentActivitiesPanel can throw a TypeError when
props.styles is undefined; update the component to provide a safe default for
styles (e.g., set styles = {} in the RecentActivitiesPanel parameter or add
RecentActivitiesPanel.defaultProps = { styles: {} }) and ensure any usage like
className={styles.panel}, styles.panelHeader, styles.list,
styles.listItemColumn, styles.activityMessage, and styles.memberMeta will not
access properties on undefined; this guarantees the activities mapping remains
safe when callers omit the styles prop.

In `@frontend/src/components/AdminMemberApproval/AdminMemberApproval.jsx`:
- Line 231: The "신청일시" column currently renders a hardcoded "-" causing loss of
the application timestamp; update the AdminMemberApproval component so the table
cell(s) for that column bind to the actual timestamp field (e.g.,
member.createdAt or member.appliedAt) in the row rendering code instead of "-"
and format it (e.g., toLocaleString or a formatDate util) for display; make the
same change for the duplicate cells referenced around the second occurrence
(lines 259-262) so both table rows show the real application datetime.
- Around line 56-60: The filter assumes member.name, member.email, and
member.studentId are non-null strings and calls toLowerCase/includes which will
throw for null or non-string values; update the filtering in AdminMemberApproval
(the pendingMembers.filter using normalizedQuery) to guard/coerce each field
before calling string methods — e.g., treat missing values as empty strings or
String(...) and only call toLowerCase/includes on the resulting string (also
ensure studentId is converted to string before calling includes) so
null/undefined/non-string fields no longer break filtering or rendering.
- Line 23: SelectedIds can persist across searches/filters causing hidden
members to be acted on; update AdminMemberApproval to clear or sanitize
selections whenever the visible member list changes: in the effect or callback
that updates the displayed members (e.g., when searchQuery/filters/pagination or
the derived visibleMembers array updates), call setSelectedIds([]) or
setSelectedIds(prev => prev.filter(id => visibleIdsSet.has(id))) so only
currently visible IDs remain selected; ensure checkbox handlers still toggle
using selectedIds/setSelectedIds and apply the same fix to the other
selection-related logic referenced (the blocks around lines 64-77 and 192-210).

In `@frontend/src/components/AdminMemberApproval/AdminMemberApproval.module.css`:
- Around line 102-107: The .tableWrap CSS hides horizontal overflow causing
right-side action columns to be inaccessible on narrow screens; update the
.tableWrap rules (refer to the .tableWrap selector) to allow horizontal
scrolling instead of clipping (enable overflow-x:auto or overflow:auto and add
touch scrolling support) and ensure the inner table can widen (e.g., keep its
intrinsic/min-width) so the action column remains reachable on mobile.

In `@frontend/src/components/AdminMemberManage/AdminMemberManage.jsx`:
- Line 240: The table header label "가입일" does not match the cell value (the code
renders the member's generation), so update the JSX in AdminMemberManage.jsx to
make them consistent: either change the <th> text "가입일" to "기수" (or the correct
label) or change the cell renderer that currently outputs generation (e.g.,
member.generation or the map item rendering) to output the join date field
(e.g., member.joinDate/createdAt). Ensure you apply the same fix for the other
occurrence noted around the second instance (the cell at the other row/column
rendering, referenced near the code that uses generation).
- Line 249: The avatar initial render can throw if member.name is null/undefined
or not a string; update the AdminMemberManage.jsx avatar rendering (the div
using styles.avatar and member.name[0]) to defensively read the initial—use
optional chaining and a safe default (e.g., derive initial with something like
const initial = (typeof member?.name === 'string' && member.name.length) ?
member.name[0] : fallbackChar) and render that initial instead, or create a
small utility/getInitial function to centralize this logic so non-string or
missing names won't break rendering.
- Line 71: Remove the console.log that prints member data to the browser (the
console.log('회원 목록 로드 성공:', nextMembers) in the AdminMemberManage component) to
avoid exposing PII; if you still need runtime visibility for debugging, use a
stripped/aggregated log (e.g., log only counts or non-identifying metrics) or
wrap detailed logs behind a debug flag that is disabled in production and ensure
nextMembers is never logged in production builds.

In `@frontend/src/components/attendance/SessionManage.jsx`:
- Around line 115-116: Date column can show "-" when roundDate is missing
because display uses s.roundDate while sorting uses s.roundStartAt; change the
display to fall back to the start timestamp. Update the cell that renders
formatDate(s.roundDate) in SessionManage.jsx to use the start-time fallback
(e.g., call formatDate(s.roundDate ?? s.roundStartAt) or a small helper that
returns formatDate(roundDate) || formatDate(roundStartAt)), so the date column
shows a value when roundStartAt exists; keep formatTime(s.roundStartAt)
unchanged.

In `@frontend/src/pages/AdminHome.jsx`:
- Around line 25-28: loadAdminHomeData currently awaits getAdminHomeData without
error handling so a failed fetch leaves the dashboard blank; wrap the await in a
try/catch inside loadAdminHomeData, call setData with a safe fallback or empty
state on failure, set an error/loading state (or invoke existing
setError/setLoading handlers) and log the error (or show a user-facing message)
so failures surface instead of silently failing; locate loadAdminHomeData,
getAdminHomeData and setData in AdminHome.jsx to implement this.

In `@frontend/src/utils/adminHomeData.js`:
- Around line 17-56: The getAdminHomeData function lacks error handling around
the api.get('/api/admin/users') call; wrap the network call in a try/catch
inside getAdminHomeData, catch and log the error (e.g., console.error) and
return a safe default payload (dashboardStats with '-' or '0' as appropriate,
empty arrays for pendingApprovals, recentActivities, quickActions, members) so
the UI won't crash; alternatively rethrow a controlled error if you prefer
caller-handled errors, but ensure getAdminHomeData and its callers are
consistent.

In `@frontend/src/utils/adminMemberManageData.js`:
- Around line 35-54: Change both approvePendingMembersBulk and
rejectPendingMembersBulk to use Promise.allSettled instead of Promise.all,
iterate the settled results to collect userIds that failed, and if any failures
exist throw an Error object augmented with a failedUserIds array (e.g.,
error.failedUserIds = [...]) so callers (like AdminMemberApproval.jsx) can
inspect which userIds failed; keep the same api.patch calls and params in the
mapped promises but replace the final await Promise.all(...) with logic that
awaits Promise.allSettled(mappedPromises), filters for results with status !==
'fulfilled', builds the failed list from the corresponding userIds array, and
throws when non-empty (or return success when all fulfilled).

---

Outside diff comments:
In `@frontend/src/contexts/AuthContext.jsx`:
- Line 27: There's a typo in the variable name "paylaod" in AuthContext.jsx;
rename it to "payload" where it's declared (const paylaod = { studentId,
password }) and update all usages of "paylaod" in the surrounding
functions/methods (e.g., any calls or references that pass this object) to the
correct "payload" identifier to avoid ReferenceErrors.
- Around line 35-46: The logout function currently only calls
setIsLoggedIn(false) inside the catch block, so on a successful
api.post('/api/auth/logout') the UI stays logged in; move or add the state
update so setIsLoggedIn(false) runs regardless of API outcome (e.g., place it in
the finally block or immediately after the await) and ensure
localStorage.removeItem('user') remains executed; update the logout function
reference in AuthContext.jsx accordingly so that setIsLoggedIn is always cleared
when logout() completes.

---

Nitpick comments:
In `@frontend/src/App.jsx`:
- Line 21: Remove the dead commented import and route entries so the codebase
has no leftover commented routing code: delete the commented import line
referencing CheckInPage (the commented "// import CheckInPage from
'./components/attendancemanage/qrmanagement/CheckInPage.jsx';") and any
corresponding commented route at the later location, and ensure there are no
other stale references to CheckInPage in App.jsx (so imports and Route
definitions only include active components).

In `@frontend/src/components/AdminExcelUpload/AdminExcelUpload.module.css`:
- Around line 116-134: The .fileName text can overflow and push buttons because
flex items need an explicit shrink/basis; update the CSS for .fileName (and/or
.selectedRow children) to allow proper shrinking by adding flex properties
(e.g., flex: 1 1 auto or flex: 1) and setting min-width: 0 on .fileName so the
ellipsis (text-overflow: ellipsis; white-space: nowrap) reliably truncates long
filenames without breaking the layout of .selectedRow.

In `@frontend/src/components/AdminHome/AdminHeader.jsx`:
- Around line 15-19: The search input in AdminHeader lacks state and an onChange
handler; add local state (e.g., const [searchQuery, setSearchQuery] =
useState('')) inside the AdminHeader component and wire an onChange handler
(e.g., handleSearchChange) that calls setSearchQuery(event.target.value) and
optionally invokes a passed prop callback (e.g., props.onSearch or
onSearchChange) to lift the value up; update the input to use
value={searchQuery} and onChange={handleSearchChange} so the search field
becomes controlled and functional.
- Around line 22-25: The small notification dot (span with className styles.dot)
is always rendered; update AdminHeader.jsx to render that span conditionally
based on a boolean indicating unread notifications (e.g., prop or state named
hasUnreadNotifications / notificationCount > 0). In the AdminHeader component,
compute or accept a boolean (hasUnreadNotifications) from props or the store and
replace the unconditional <span className={styles.dot} /> with a conditional
render like: render the dot only when hasUnreadNotifications is true; ensure the
boolean is correctly derived (e.g., notificationCount > 0) and remains
accessible to the button that contains the Bell icon.

In `@frontend/src/components/AdminHome/AdminSidebar.jsx`:
- Around line 73-85: Replace the manual active-class logic using Link and
isDevSection in AdminSidebar with react-router-dom's NavLink: import NavLink,
swap the two Link elements for NavLink components (the ones rendering "회장용" and
"개발자용"), and use NavLink's className callback to apply styles.tabButton plus
styles.tabActive when the link is active instead of relying on isDevSection;
ensure the active-detection matches the same paths ("/admin" and
"/admin/dev/logs") and remove or stop depending on the manual isDevSection-based
class toggling once NavLink is used.

In `@frontend/src/components/AdminHome/MemberList.jsx`:
- Around line 8-25: Replace the inline styles in the MemberList component with
classNames from a CSS module: create (or import) a MemberList.module.css and
move table, thead, th, td and tr styles there, then update the JSX in
MemberList.jsx to use className attributes (e.g., className={styles.table},
styles.th, styles.td, styles.row) instead of the inline style objects used on
the <table>, <th>, <td>, and <tr> elements and keep the members.map rendering
logic intact.

In `@frontend/src/components/AdminHome/PendingApprovalsPanel.jsx`:
- Around line 8-31: handleApprove and handleReject allow repeated rapid clicks
because there is no "processing" state per member; add a local state (e.g.,
useState of a Set or map like processingIds) to track which member IDs are being
processed, check and early-return if the member.id is already in processing, add
the member.id to processingIds before the async call and remove it in a finally
block, and update the approve/reject buttons' disabled prop (and show a spinner
if desired) by checking processingIds.has(member.id) so the UI prevents
duplicate requests for the same member while the request is in-flight.
- Around line 42-68: The panel currently renders an empty list when
members.length === 0; update the PendingApprovalsPanel component to show a clear
empty-state message instead of an empty UL: add a conditional branch around the
members rendering so that when members.length === 0 you render a div or
paragraph (styled with a new or existing styles.emptyState) with a short message
like "대기 중인 회원이 없습니다" and optional helper text/CTA; keep the existing list
rendering (with members.map, listItem keys, and handlers handleApprove /
handleReject) for the non-empty case.

In `@frontend/src/components/AdminHome/RecentActivitiesPanel.jsx`:
- Around line 7-14: The RecentActivitiesPanel currently renders an empty <ul>
when activities is an empty array; update the component (RecentActivitiesPanel /
the render that maps over activities) to detect when activities.length === 0 and
render a clear empty-state UI (e.g., a <div> or <li> with a friendly message and
optional icon using styles.emptyState or styles.listItemEmpty) instead of the
empty list so users see a helpful message when there are no activities.

In `@frontend/src/components/AdminMemberManage/AdminMemberManage.module.css`:
- Around line 26-35: Add keyboard-focus-visible styles for the interactive form
controls to improve accessibility: update the CSS for .searchInput and
.filterSelect and any action button classes (e.g., .actionButton or the buttons
used in this component) to include a :focus-visible rule that provides a
high-contrast visible indicator (such as a distinct outline or box-shadow and no
outline: none) and preserves existing sizing/spacing; ensure the style is
applied where similar controls exist later in the file (the block referenced by
the review) so keyboard users can clearly see focus state across search, filter
and action controls.

In `@frontend/src/components/AdminRoute.jsx`:
- Around line 5-8: The isAdminRole function currently hardcodes the 'PRESIDENT'
string; extract that into a reusable policy constant (e.g., ADMIN_ROLES or
ADMIN_ROLE) and reference the constant from isAdminRole instead of the literal.
Create a top-level constant in the module (or import from a central config/env)
such as ADMIN_ROLES = ['PRESIDENT'] (or read from process.env/feature flag) and
change isAdminRole to check membership (use normalizedRole and
includes/contains) so role policy can be updated without editing AdminRoute.jsx.

In `@frontend/src/components/Sidebar.jsx`:
- Around line 33-50: The Sidebar currently calls /api/user/details in the
useEffect (checkAdminRole) causing duplicate requests; instead, expose and use
the role stored in AuthContext (e.g., add or use userRole in AuthContext state)
and remove the checkAdminRole effect and api.get from Sidebar; in Sidebar
replace the isPresident logic to derive from the context value (useAuth ->
userRole, then compute userRole?.toUpperCase() === 'PRESIDENT') so only
AuthContext performs the network call.

In `@frontend/src/pages/AdminExcelUpload.module.css`:
- Around line 1-33: Extract the duplicated CSS (.layout, .mainArea, .contentArea
and the media queries) from AdminExcelUpload.module.css and
AdminMemberApproval.module.css into a new shared stylesheet
AdminLayout.module.css; move those rules exactly as-is into
AdminLayout.module.css, then update the pages/components that import
AdminExcelUpload.module.css and AdminMemberApproval.module.css to also import
layoutStyles from '../../styles/AdminLayout.module.css' (or the appropriate
relative path) and replace usages of .layout, .mainArea, and .contentArea to use
layoutStyles.layout, layoutStyles.mainArea, layoutStyles.contentArea; keep any
page-specific rules in their original module files (or remove duplicates) so
only common layout rules remain in AdminLayout.module.css.

In `@frontend/src/utils/adminHomeData.js`:
- Around line 3-8: The current recentActivities constant is static placeholder
data; either add a clear TODO comment above recentActivities indicating it must
be replaced by the real API response when available, or replace the constant
with an async fetch function (e.g., fetchRecentActivities or
getRecentActivities) that calls your backend endpoint (e.g.,
'/api/recent-activities'), parses JSON, returns the array, and returns a safe
fallback (empty array) on error; update exports to expose the async function and
remove/stop using the hardcoded recentActivities constant.

In `@frontend/src/utils/adminUserApi.js`:
- Around line 4-38: This file duplicates endpoints already implemented in
adminMembersData.js; refactor by extracting shared API calls into a single
common module (e.g., adminUsersApi or reuse adminMembersData) and convert
functions here—getAdminUsers, updateAdminUserRole, updateAdminUserStatus,
promoteAdminUserSenior, deleteAdminUser—into thin wrappers that import and
re-export or delegate to the canonical implementations; ensure parameter names
and return shapes match the original functions and update callers to import the
shared module to avoid drift when endpoints or response formats change.

In `@frontend/src/utils/attendanceList.js`:
- Around line 3-12: The exported async function attendanceList should be renamed
to a clearer async name (e.g., fetchAttendanceList or getAttendanceList) to
signal it returns a Promise; update the function declaration/export from
attendanceList to the chosen name and update all call sites/imports that
reference attendanceList accordingly (search for attendanceList usages), leaving
the request logic (api.get('/api/attendance/me')) and error handling unchanged.